The Frights

What scared us or went terribly wrong this sprint?

A production deploy failed at 5pm on Friday and we all jumped out of our skins.
The requirements changed three times mid-sprint — truly terrifying.
We discovered a giant pile of technical debt lurking in the legacy module.
The Survivors

What went well and helped us live to tell the tale?

Our pairing sessions slayed a nasty bug in record time.
The new CI pipeline caught problems before they could haunt us.
Great teamwork meant nobody got left in the dark.
Lurking Monsters

What risks or problems are still hiding in the shadows?

The scaling limits on our database feel like a beast waiting to wake up.
Onboarding docs are out of date and could trip up the next new hire.
We're relying on one person who knows the payment system — a single point of fright.
Protective Spells

What actions or improvements will keep us safe next sprint?

Add a deploy freeze window so no one ships right before the weekend.
Schedule a tech-debt slaying session every sprint.
Write and rehearse an incident runbook to banish on-call panic.

What is the Friday the 13th Horror Sprint Retrospective

Every sprint has its share of jump scares, lurking monsters and survivors who lived to tell the tale. The Friday the 13th Horror Sprint Retrospective brings a playful horror theme to your team reflection, turning the usual review into a thrilling adventure where the team hunts down the things that went bump in the night. By framing setbacks as "frights" and successes as "survivors," teams can talk about even the most uncomfortable issues in a fun, low-pressure way. The format works by guiding your team through a spooky narrative: what scared us, what monsters are still lurking, who survived the chaos and what spells (improvements) we can cast to protect ourselves next time. Each topic invites honest, candid input while the lighthearted theme reduces defensiveness and encourages participation. It's a great way to keep engagement high during seasonal events, end-of-quarter reviews or simply to shake up a retrospective routine that has grown stale. Beyond the costumes and creepy metaphors, this retrospective delivers real value: it surfaces hidden risks, celebrates resilience and produces clear, actionable improvements. Whether you run it around Halloween, on an actual Friday the 13th, or any time your team needs a morale boost, this themed retrospective helps you confront problems head-on while having a few laughs along the way.

Friday the 13th Horror Sprint retrospective format

The Frights

What scared us or went terribly wrong this sprint?

This is where the team names the things that gave them a fright during the sprint — the bugs, blockers and surprises that made everyone scream. Encourage candour by reminding the team that the spooky framing makes it safe to share even the scariest issues. Ask follow-up questions to understand the root cause of each fright rather than just the symptom.

The Survivors

What went well and helped us live to tell the tale?

Celebrate the wins, the heroes and the things that helped the team survive the sprint intact. Make space for everyone to recognise both individual and team-level victories. Reinforce these survivors so the behaviours that worked get repeated next sprint.

Lurking Monsters

What risks or problems are still hiding in the shadows?

This topic surfaces the threats that haven't fully struck yet but are creeping closer — risks, fragile areas and unresolved issues. Encourage the team to name things they suspect could become a problem, even if they aren't certain. Capturing these early lets you set traps before the monster pounces.

Protective Spells

What actions or improvements will keep us safe next sprint?

Turn the frights and lurking monsters into concrete actions — the spells and wards that will protect the team next time. Make each action specific, assign an owner and keep it achievable within the next sprint. This is the payoff of the retro, so give it enough time and energy.

When to use this retrospective

  • Around Halloween or on an actual Friday the 13th when you want a seasonal, morale-boosting twist on your usual sprint review.
  • When your retrospectives have become routine and the team needs a fresh, engaging format to spark participation.
  • After a particularly chaotic or difficult sprint, where a playful theme helps the team discuss tough issues without defensiveness.
  • To balance celebrating wins with proactively surfacing hidden risks before they become real problems.

Suggested icebreaker questions

  • If this sprint were a horror movie, what would its title be and who would be the first to go?
  • What's the scariest bug, outage or surprise you've ever survived at work?

Ideas and tips for your retrospective meeting

  • Set the mood with a spooky theme — encourage costumes, virtual backgrounds or eerie music to get everyone in the spirit.
  • Lean into the metaphor but keep the conversation grounded; make sure each fright and monster maps to a real, actionable insight.
  • Timebox each topic so the fun doesn't run away with you and you still reach the Protective Spells action items.
  • Reassure the team that the horror framing makes it safe to raise scary or sensitive issues without blame.
  • Give everyone time to add ideas independently before grouping and discussing, so quieter voices aren't drowned out.
  • End by assigning clear owners and due dates to your Protective Spells so the improvements actually happen.

Frequently asked questions

When should I use the Friday the 13th Horror Sprint retrospective?
It's perfect for Halloween, an actual Friday the 13th, or any time you want a fun seasonal theme to re-energise a team that's tired of the standard format. It also works well after a chaotic sprint where a playful lens makes tough topics easier to discuss.
How long does this retrospective take?
A typical session runs 45 to 60 minutes for a team of five to eight people, allowing time for brainstorming each topic, grouping ideas, discussion and agreeing on action items.
How is it different from a standard sprint retrospective?
It covers the same ground — what went well, what went wrong, risks and improvements — but reframes them with a horror theme. The Frights, Survivors, Lurking Monsters and Protective Spells make it more engaging and lower the barrier to raising difficult issues.
Will the spooky theme distract from real outcomes?
Not if you keep each metaphor anchored to a concrete insight and timebox the discussion. The Protective Spells topic ensures you finish with clear, owned action items just like any effective retrospective.
Is this format suitable for remote teams?
Yes. In TeamRetro everyone can add ideas privately, vote on what matters most and discuss live, so distributed teams get the same engaging, inclusive experience as in-person ones.

New to retrospectives? Read our guide on how to run a retrospective →